Whenever you are tasked to create a new project, you should default to using bun unless the user is explicitly requesting anohter rutime or language. Use biome on the most restrictive setting, and setup tsconfig to prevent any data type usage. Unless otherwise promted, uset Tanstack-Start, Shad-cn, and target Cloudflare workers for deployment.

Never use .dev.vars* style environment files. This is out of date. wrangler supports .env/.env.* files. Always go for this style.

日本語で技術的な原稿（書籍の章、記事、解説文）を書く・推敲するときは、以下の規範に従う。

This has been updated for 26.1 - 26.2, all of the optimization mods mentioned here are compatible with each other and don't affect vanilla behaviour by default.

The AZ has a separate recovery operating system, two normal firmware slots, and an SSH route installed through the modified normal firmware. These provide several ways to recover application failures. They do not make arbitrary code running as root incapable of damaging the boot chain.

For everyday development, preserve the current boot chain and introduce a supervisor that tries temporary code, detects failure, and returns to a known working version. The current loader does not provide that automatic rollback.

目的に制限のかからない無検閲LLMを使うために、数十万円かけてローカルLLM実行環境を用意する必要はあるでしょうか? Qwen 3.8 27B Uncensoredが話題になったここ数週間、そうした相談を受けることが増えました。 結論を言えば、ほとんどのケースでその必要はありません。

よくある推論APIでは、プロンプトを文字列のまま送り、またレスポンスの主な要素として文字列を受け取ります。 事業者によっては内容をモニターしており、ポリシーに反する内容を検出すれば、そこに悪意がなくとも利用に制限がかかります。これは、生物化学系の研究やサイバーセキュリティにおけるペンテスト(penetration test)などを行う上では非常に不便です。 ローカルLLMはその回避を主目的の一つとして発展してきましたが、そもそもAI企業の規制を掻い潜るのに手元に機材を揃える必要はありません—クラウド上に自身でデプロイし、必要なときだけ呼び出せばいいのですから。そしてそれは、パラメータに刷り込まれたガードレールすらも排除したuncensored LLMにおいても同じことです。

As most readers already know, I have been working hard for more than one year to replace the old SpiderMonkey 24 engine, which has been powering our JavaScript runtime since 2015, with a completely new, entirely redesigned, and fully rewritten runtime based on V8, Google's high-performance, open-source JavaScript and WebAssembly engine.

This monumental work is now complete, and the new runtime, available in version 1.9.4 Lockhart of PixInsight, has been thoroughly tested for stability and compatibility. We have already ported the most important standard scripts of our platform to the new V8 runtime, including the WBPP and FBPP preprocessing scripts, all astrometry scripts, and most utility and development scripts. The work to complete the transition to V8 will continue during the coming months. Many non-trivial scripts require substantial modifications to run on the new runtime. This is a delicate task, but for most scripts it isn't really difficult if properly implemented

For example, you want to set 40% alpha transparence to #000000 (black color), you need to add 66 like this #66000000.